Trunk Attributes

System-generated, protected field. Lists the Service Numbers that are referred to in the Digital Trunks form or Analog Trunks form.

To use the Trunk Service Number for a Release Link trunk, specify the type of trunk. Use "DPN" for DPNSS trunks or "E&M" for E&M (including Digital E&M trunks) trunks. Select "No" if the trunk is not a Release Link trunk.

No

Indicates the EHDU service type that the trunk uses when handling calls for External Hot Desk Users (EHDU).

Select "Off"' to require EHDUs users to log in using their assigned DN and PIN.

Select "Trusted" if the trunk is trusted. The EHDU user is automatically logged in.

Select "Non-Trusted" if the trunk is not-trusted. The EHDU user is required to log in using the assigned PIN.

Select "Trusted FOPBX" if the mobile carrier is trusted. The EHDU user is automatically logged in.

Select "Non-Trusted FOPBX" if the mobile carrier is non-trusted. The EHDU user is required to log in using the PIN.

For more information, see Call Recognition Service.

Off

Select "On" to enable the DID Service, which will redirect incoming DID calls to assigned destination numbers, based on the mapping configured in the DID Service form.

This option should be enabled only on ingress trunking gateways.

NOTES

• The Trunks Answer Point parameters and the DID Service are mutually exclusive. If this field is set to "On", all Trunk Answer Point fields in this form (Dial-In and Non-Dial-In) must be set to 0 (zero).

• It is recommended that before using the DID Service feature, all nodes in the network (or at least the resilient pair related to the specific DN) be upgraded to Mitel MiVoice Business Release 7.0.

Off

Select On to enable the Caller Based Routing service for a selected trunk. The switch controls whether Caller Based Routing must be enabled for a particular trunk or not. ensuring that toll fraud does not occur.

CAUTION: Enabling the Caller Based Routing feature could lead to toll fraud. The system administrator must exercise caution before enabling this feature.

Off

Enter the COS number that defines the required options for the trunk (mandatory field).

1

Enter the COR number for the trunk. This COR number must not have been assigned to a station (mandatory field).

1

Select the maximum baud rate which the trunks associated with the trunk service number will accept. Allowed values are "110", "150", "200", "300", "600", "1200", "1800", "2400", "4800", and "9600".

Baud Rate for DASS trunks should be 9600.

300

Enter an intercept number which will link the trunk service number to a version of the Intercept Handling form.

1

Enter any valid station, hunt group pilot number, DISA number, or System Speed call number to which incoming trunk calls can be routed during the Day service. An entry is required for each service mode (Day, Night 1, Night 2). Any trunk may have the same Answer Points under each mode of service.

NOTES

• A Hot Desk user DN cannot be a Trunk Answer Point. If a Hot Desk user is logged in on a Registration DN that is a Trunk Answer Point, calls will follow out-of-service handling.

• The Answer Point and Digit Modification columns are mutually exclusive. If one is filled out, the other must be left blank for any given trunk. Both the Answer Point and Digit Modification columns are left blank if the trunk is outgoing only.

Blank

Enter any valid station, hunt group pilot number, DISA number, or System Speed call number to which incoming trunk calls can be routed during the Night 1 service. An entry is required for each service mode (Day, Night 1, Night 2). Any trunk may have the same Answer Points under each mode of service.

The above notes for Day service answer point also apply.

Blank

Enter any valid station, hunt group pilot number, DISA number, or System Speed call number to which incoming trunk calls can be routed during Night 2  service. An entry is required for each service mode. Any trunk may have the same Answer Points under each mode of service.

The above notes for Day service answer point also apply.

Blank

Number of leading digits to remove from the digit stream received from the Central Office or remote system. The maximum number of digits is 26. Dial-in trunks used as incoming trunks must always have an entry in the Absorb column. (You must enter "0" if no digits are to be absorbed. If you leave this field as Blank, calls will fail).

Blank

The actual digits to insert as leading digits to form a Directory Number or hunt group Pilot Number. The maximum number of digits is 7.

NOTE: The Answer Point and Digit Modification columns are mutually exclusive. If one is filled out, the other must be left blank for any given trunk. Both the Answer Point and Digit Modification columns are left blank if the trunk is outgoing only. If a Dial-In trunk does not require digit modification, enter "0" in the Absorb field and leave the Insert field blank.

Blank

Enter a valid voice mail hunt group directory number (1-26 digits comprising 0-9, *,#) to which incoming calls can be routed, for example MiCollab Nupoint UM or MiVoice Business embedded voice mail.

NOTES

• The Dial-In Trunks Insert Forwarding Information field must be enabled to program Dial-In Trunks Answer Point.

• The Dial-In Trunks Answer point can be any valid or invalid number, however to achieve direct to voice mail the DN must be a voice mail Hunt group DN.

• The Dial-In Trunks Answer Point and Non-Dial In Trunks Answer Point fields are mutually exclusive. An attempt to fill in both fields yields the following error message: It is invalid to fill in both the Non-dial In and Dial-In Fields.

Blank

Choose "Yes" to direct the call to the answer point with the forwarding from information included.

NOTES

• The call preserves the original ‘Forward From’ information if it is forwarded always by multiple DNs before being directed to the final destination. It is the final destination DN (while ringing) that displays the ‘Forward from’ information of the first DN that forwarded the call.

• If the incoming call is a forwarded call, the forwarding information received is always displayed regardless of whether this option is set.

No